Recording medium, playback device, and playback method

ABSTRACT

At least one video stream that is encoded video information, and a management information file indicating attributes relating to the entire recording medium, are recorded in a recording medium. The management information file includes attribute information indicating whether the dynamic range of luminance of an initial video stream, which is played first out of the at least one video stream when the recording medium is inserted into a playback device, is a first dynamic range, or a second dynamic range that is broader than the first dynamic range.

BACKGROUND

1. Technical Field

The present invention relates to a recording medium in which is recordedan encoded video stream, a playback device that plays the video stream,and a playback method.

2. Description of the Related Art

Technology relating to DVDs has conventionally been disclosed (e.g.,Japanese Unexamined Patent Application Publication No. 9-282848).However, further improvement was needed with this technology.

SUMMARY

In one general aspect, the techniques disclosed here feature a recordingmedium, in which are recorded at least one video stream that is encodedvideo information, and a management information file indicatingattributes relating to the entire recording medium. The managementinformation file includes attribute information indicating whether thedynamic range of luminance of an initial video stream, which is playedfirst out of the at least one video stream when the recording medium isinserted into a playback device, is a first dynamic range, or a seconddynamic range that is broader than the first dynamic range.

According to the above configuration, further improvement can berealized.

It should be noted that general or specific embodiments may beimplemented as a system, a method, an integrated circuit, a computerprogram, a storage medium, or any selective combination thereof.

Additional benefits and advantages of the disclosed embodiments willbecome apparent from the specification and drawings. The benefits and/oradvantages may be individually obtained by the various embodiments andfeatures of the specification and drawings, which need not all beprovided in order to obtain one or more of such benefits and/oradvantages.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating an SD-DVD structure;

FIG. 2 is a schematic diagram for describing navigation informationembedded in an MPEG stream, which is AV data;

FIG. 3 is a schematic diagram illustrating a VOB structure in a DVD;

FIG. 4 is a diagram illustrating a data hierarchy of a BD-ROM;

FIG. 5 is a diagram illustrating a structure of logical data recorded ina BD-ROM;

FIG. 6 is a diagram illustrating an overview of a basic configuration ofa BD-ROM player that plays BD-ROMs;

FIG. 7 is a block diagram where the configuration of the playerillustrated in FIG. 6 is detailed;

FIG. 8 is a diagram illustrating application space of a BD-ROM;

FIG. 9 is a diagram illustrating the configuration of an MPEG stream(VOB);

FIG. 10 is a diagram illustrating the configuration of packs in an MPEGstream;

FIG. 11 is a diagram for describing the relationship between AV data andplayer configuration;

FIG. 12 is a diagram for describing a VOB data continuous supply modelusing a track buffer;

FIG. 13 is a diagram illustrating the internal structure of a VOBmanagement information file;

FIG. 14 is a diagram for describing the details of VOBU information;

FIG. 15 is a diagram for describing an address information acquisitionmethod using a time map;

FIG. 16 is a diagram illustrating the configuration of a playlist;

FIG. 17 is a diagram illustrating the configuration of an event handlertable;

FIG. 18 is a diagram illustrating the configuration of BD.INFO which isoverall BD-ROM information;

FIG. 19 is a diagram illustrating the structure of a global eventhandler table;

FIG. 20 is a diagram illustrating an example of a time event;

FIG. 21 is a diagram illustrating an example of a user event due to auser having operated a menu;

FIG. 22 is a diagram illustrating an example of a global event;

FIG. 23 is a diagram for describing the functional configuration of aprogram processor;

FIG. 24 is a diagram illustrating a list of system parameters (SPRM);

FIG. 25 is a diagram illustrating an example of a program in an eventhandler according to control of a menu screen having two selectionbuttons;

FIG. 26 is a diagram illustrating an example of a program in an eventhandler relating to a menu selection user event;

FIG. 27 is a flowchart illustrating the flow of basic processing forplayback of AV data in a BD-ROM player;

FIG. 28 is a flowchart illustrating the flow of processing in a BD-ROMplayer from starting to play a playlist until ending playing of the VOB;

FIG. 29A is a flowchart illustrating the flow of processing relating toa time event in a BD-ROM player;

FIG. 29B is a flowchart illustrating the flow of processing relating toa user event in a BD-ROM player;

FIG. 30 is a flowchart illustrating the flow of processing subtitle datain a BD-ROM player;

FIGS. 31A and 31B are diagrams describing arrays of NAL units;

FIG. 32 is a diagram for describing an example of MPEG-2 TS multiplexingof an HDR video stream;

FIG. 33 is a diagram for describing an example of MPEG-2 TS multiplexingof an HDR video stream;

FIG. 34 is a diagram for describing an example of MPEG-2 TS multiplexingof an HDR video stream;

FIG. 35 is a diagram for describing an example of MPEG-2 TS multiplexingof an HDR video stream;

FIG. 36 is a diagram for describing an example of MPEG-2 TS multiplexingof an HDR video stream;

FIG. 37 is a diagram for describing an example of MPEG-2 TS multiplexingof an HDR video stream;

FIG. 38 is a diagram for describing an example of MPEG-2 TS multiplexingof an HDR video stream;

FIG. 39 is a diagram for describing management information of an HDRvideo stream;

FIG. 40 is a diagram for describing management information of an HDRvideo stream and the content thereof;

FIG. 41 is a diagram for describing management information of an HDRvideo stream and the content thereof;

FIG. 42 is a diagram for describing synchronous playback of an HDR videostream and an enhanced video stream thereof;

FIG. 43 is a diagram for describing synchronous playback of an HDR videostream and an enhanced video stream thereof; and

FIG. 44 is a diagram for describing a decoder model of an HDR videostream.

DETAILED DESCRIPTION Underlying Knowledge Forming Basis of the PresentInvention

The present Inventors found that the following problem occurs relatingto the recording media such as DVD and the like described in the“Background Art” section.

Most representative of information recording media recording video datais the DVD (hereinafter, may also be referred to as “StandardDefinition” (SD)-DVD). A conventional DVD will be described below.

FIG. 1 is a diagram illustrating the structure of an SD-DVD. As shown inthe lower tier in FIG. 1, the DVD disc has a logical address spaceprovided between a read-in and a read-out. Volume information of a filesystem is recorded from the beginning of the logical address space, andafter that is recorded application data such as video, audio, and soforth.

The file system is an arrangement for managing data, that is stipulatedby Standards such as ISO9660, Universal Disc Format (UDF), and so forth,and is an arrangement to express data on the disc in increments calleddirectories or files. There are file systems called File AllocationTables (FAT) and NT File System (NTFS) in everyday-use personalcomputers (PC) as well, whereby data recorded in a hard disk areexpressed on the computer as structures called directories or files,thereby improving usability.

In the case of an SD-DVD, both UDF and ISO9660 file systems are used.The two together are also referred to as “UDF bridge”. The recorded datais arranged so that the data can be read out by a file system driveraccording to either UDF or ISO9660. Note that the DVD used here is a ROMdisc for packaged media, to which writing is physically impossible.

Data recorded in the DVD can be viewed through the UDF bridge asdirectories or files such as illustrated to the upper left in FIG. 1.Immediately below the root directory (“ROOT” in FIG. 1) is placed adirectory called “VIDEO_TS”, and it is here that DVD application data isrecorded. Application data is recorded as multiple files, primary filesbeing the following types of files.

VIDEO_TS.IFO Disc play control information file VTS_01_0.IFO Video titleset #1 play control information file VTS_01_0.VOB Video title set #1stream file . . .

As shown in the above example, two suffixes are stipulated. “IFO” is asuffix indicating that the file has play control information recordedtherein, and “VOB” is a suffix indicating that the file has an MPEGstream, which is AV data, recorded therein.

Play control information is information attached to the AV data, such asinformation to realize interactivity employed with the DVD (technologyto dynamically change playing in response to user operations), metadata,and so forth. Play control information is commonly referred to asnavigation information regarding DVDs.

The play control information files include the “VIDEO_TS.IFO” thatmanages the entire disc, and the “VTS_01_0.IFO” that is play controlinformation for individual video title sets. Note that multiple titles,in other words, multiple different movies and tunes, can be recorded ina single disc in the case of DVD. “01” in the file name body indicatesthe No. of the video title set, and in the case of the video title set#2, for example, this is “VTS_02_0.IFO”.

The upper right portion in FIG. 1 is DVD navigation space in theapplication layer of the DVD, and is the logical structure space wherethe aforementioned play control information is loaded. Informationwithin the “VIDEO_TS.IFO” is loaded in the DVD navigation space as VIDEOManager Information (VMGI), as well as are “VTS_01_0.IFO” and playcontrol information existing for each of other video title sets as VideoTitle Set Information (VTSI).

Described in the VTSI is Program Chain Information (PGCI) which isinformation of a play sequence called Program Chain (PGC). PGCI is madeup of a set of Cells and a type of programming information calledcommands.

A Cell itself is information indicating a partial section or a wholesection of a VOB (short for Video Object, and indicates an MPEG stream),and playing a Cell means to play the section of this VOB instructed bythe Cell.

Commands are processed by a virtual machine of the DVD, and are close toJava (a registered trademark) Script and so forth executed in browsersto display Web pages, for example. However, while Java (registeredtrademark) Script performs window or browser control (e.g., opening anew browser window, etc.) besides logical operations, DVD command differin that they only execute playback control of AV titles, e.g.,instructing a chapter to play or the like, for example, besides logicaloperations.

A Cell has the start and end addresses (logical addresses) of a VOBrecorded in the disc as internal information thereof. A player reads outdata using the start and end address information of the VOB described inthe Cell, and executes playback.

FIG. 2 is an overview for describing navigation information embedded inan MPEG stream, which is AV data. Interactivity, which is a feature ofthe SD-DVD, is realized not only by the navigation information recordedin the aforementioned “VIDEO_TS.IFO” and “VTS_01_0.IFO” and so forth.Several important sets of information are multiplexed in the VOB alongwith video and audio data, using a dedicated carrier called navigationpacks (called navi-pack or NV_PCK).

A menu screen will be described here as a simple example ofinteractivity. Several buttons are shown on the menu screen, withprocessing to be executed defined for each button when that button isselected.

One button is selected on the menu screen (a translucent color isoverlaid on the selected button in highlight that button, indicating tothe user that button is in a selected state), and the user can move thebutton in the selected state to any of the buttons above or below, tothe left or to the right, using arrow keys on a remote controller. Usingthe arrow keys of the remote controller to move the highlight to thebutton to be selected and executed, and okaying (pressing an OK key)executes the program of the corresponding command. Generally, playbackof a corresponding title or chapter is executed by the command.

The upper left portion in FIG. 2 shows an overview of information storedin an NV_PCK. Highlight color information, information of individualbuttons, and so forth, are included in the NV_PCK. Color paletteinformation is described in the highlight color information, specifyingthe highlight translucent color to be displayed overlaid.

Described in the button information are rectangular region informationwhich is the position information of each button, moving informationfrom that button to other buttons (specification of destination buttonscorresponding to each operation of the arrow keys by the user), andbutton command information (a command to be executed when that button isokayed).

The highlight on the menu screen is created as an overlaid image, asillustrated to the upper right portion in FIG. 2. The overlaid image isan object where rectangular region information of button information hasbeen given color in color palette information. This overlaid image iscomposited with the background image illustrated at the right portion inFIG. 2, and displayed on the screen.

The menu screen of a DVD is realized as described above. The reason whypart of the navigation data is embedded in the stream using an NV_PCK isas follows. That is, to realize without problem processing wheresynchronization timing readily becomes problematic, such as dynamicallyupdating menu information synchronously with the stream, for example,displaying a menu screen for just five to ten minutes partway throughplaying a movie.

Another major reason is to improve user operability, such as to storeinformation for supporting special playback in an NV_PCK, so that AVdata can be decoded and played smoothly during non-normal playback, suchas fast-forward and fast-rewind while playing the DVD.

FIG. 3 is a schematic diagram illustrating the configuration of a VOB ina DVD. Data such as video, audio, and subtitles ((1) in FIG. 3) arepacketized and packed according to the MPEG system (ISO/IEC13818-1)Standard ((2) in FIG. 3), and these are multiplexed to form a singleMPEG program stream ((3) in FIG. 3), as illustrated in FIG. 3. TheNV_PCKs including button commands for realizing interactivity are alsomultiplexed along with these, as described above.

A feature of multiplexing in the MPEG system is that the individualpixels of data that are multiplexed are in a bit string based ondecoding order, but the bit string is not necessarily formed in playbackorder, that is to say decoding order, among the multiplexed data, i.e.,among the video, audio, and subtitles.

This is due to a decoder model of the MPEG system stream ((4) in FIG. 3,generally referred to as System Target Decoder or STD) has decoderbuffers corresponding to each elementary stream after demultiplexing,that temporarily stored the data until the decoding timing. Thesedecoder buffers have different sized according to each of the individualelementary streams, having 232 kB for video, 4 kB for audio, and 52 kBfor subtitles. Accordingly, the data input timing to each decoder bufferdiffers among the individual elementary streams, so there is discrepancybetween the order of forming the bit string as the MPEG system stream,and the timing of displaying (decoding). That is to say, the subtitledata multiplexed along with the video data is not necessarily decoded atthe same time.

Now, in a large-capacity recording media such as a Blu-ray (registeredtrademark) disc, there is a possibility that extremely high-definitionvideo information can be stored. Note that Blu-ray (registeredtrademark) disc, is also called BD or BD-ROM. For example, it isconceivable that video information such as 4K (video information havingresolution of 3840×2160 pixels) or HDR (high-luminance videoinformation, generally called High Dynamic Range) may be stored in a BD.However, there are various methods to express luminance including HDR,and there has been no format that can record and manage videoinformation of these realization methods efficiently as a video stream.Accordingly, there is a problem that the playback device cannot suitablyexpress luminance according to the type of video stream recorded in therecording medium such as the BD (the above-described realizationmethod).

The Present Inventors studied the following improvement measures tosolve the above problem.

According to an aspect of the present disclosure, in a recording mediumare recorded at least one video stream that is encoded videoinformation, and a management information file indicating attributesrelating to the entire recording medium. The management information fileincludes attribute information indicating whether the dynamic range ofluminance of an initial video stream, which is played first out of theat least one video stream when the recording medium is inserted into aplayback device, is a first dynamic range, or a second dynamic rangethat is broader than the first dynamic range.

Accordingly, referencing the attribute information in the managementinformation file such as the BD.INFO file (e.g., is_HDR) enablesdetermination of the dynamic range of luminance of the initial videostream. For example, without analyzing the initial video stream. Forexample, whether the dynamic range of luminance of the initial videostream is SDR or HDR can be easily determined. Thus, when the recordingmedium is inserted into the playback device, the playback devicereferences the attribute information of the management information file,which enables negotiation based on HDMI (registered trademark) to bespeedily performed with a display such as a television or the like, andthe initial video stream to be played. In this way, video streams and beefficiently recorded and managed, even in cases where there are variousforms for expressing the luminance of video streams.

Also, according to an aspect of the present disclosure, in a recordingmedium are recorded at least one video stream that is encoded videoinformation, and a management information file indicating attributesrelating to the entire recording medium. The management information fileincludes attribute information indicating whether or not each of apredetermined plurality of types of video streams relating to dynamicrange of luminance are included in the at least one video stream.

Accordingly, referencing the attribute information in the managementinformation file in the BD.INFO file (e.g., HDR_type) enables easydetermination of what types of video streams are recorded in the BD.That is to say, determination can be made without analyzing the videostreams recorded in the BD. For example, determination can be easilymade regarding whether or not an SDR video stream, an HDRb video stream,an HDRe video stream, and an enhanced video stream, are recorded in theBD. Thus, the playback device references the attribute information inthe management information file, which enables negotiation based on HDMI(registered trademark) to be speedily performed with a display such as atelevision or the like, and the video streams stored in the BD to beplayed. In this way, video streams can be efficiently recorded andmanaged, even in cases where there are various forms for expressing theluminance of video streams.

Also, according to an aspect of the present disclosure, in a recordingmedium are recorded a base video stream that is encoded videoinformation, an enhanced video stream that is encoded video information,for enhancing luminance of the base video stream, and a managementinformation file in which is described a playback path of the base videostream. A playback path of the enhanced video stream is furtherdescribed in the management information file so as to be played at thesame time as the base video stream. For example, a first sectionincluded in the playback path of the base video stream, and a secondsection included in the playback path of the enhanced video stream, aredescribed in the management information file in a mutually correlatedmanner, and playback time of the first section and the second section isthe same. Specifically, a playback start time of the first section, anda playback start time of the second section, that are the same time aseach other, are described in the management information file. Also, aplayback end time of the first section, and a playback end time of thesecond section, that are the same time as each other, are described inthe management information file.

Accordingly, not only the playback path of the base video stream (HDRvideo stream (HDRb)) but also the playback path of the enhanced videostream described as SubPL information can also be easily identified byreferencing the management information file such as the PlayList file.Therefore, for example, the playback device can easily and appropriatelymultiplex the enhanced video stream on the base video stream byreferencing the management information file, and consequently canappropriately play video information having a wide dynamic range. Inthis way, video streams can be efficiently recorded and manages even incases where there are various forms for expressing luminance of videostreams.

The base video stream and the enhanced video stream may be multiplexedin the same transport stream.

Accordingly, the base video stream and enhanced video stream can beclearly correlated, and video information having a wide dynamic rangecan be played in an appropriate manner.

Also, a playback device according to an aspect of the present disclosureincludes a video playback unit that reads out and plays the initialvideo stream based on the management information file.

Here, the video playback unit may include a first decoding unit thatreads out and decodes the base video stream and the enhanced videostream from the recording medium, a second decoding unit that reads outand decodes encoded graphics data from the recording medium, aprocessing unit that converts color of a predetermined number of levelsindicated by the decoded graphics data, into color of a predeterminednumber of levels in accordance with a video plane that stores a videostream on which the graphics data is to be superimposed, and asuperimposing unit that superimposes the decoded enhanced video streamon the decoded base video stream and stores at the video plane, andfurther superimposes graphics data expressed by color of the convertednumber of levels on the video stream stored at the video plane.

Accordingly, the playback device according to the present embodiment canmake the color of subtitles, for example indicated by graphics data, toappropriately match the color of wide-dynamic-range video informationrealized using an enhanced video stream.

These general or specific aspects may be realized by a device, method,system, integrated circuit, computer program, or computer-readablerecording medium such as a CD-ROM, and may be realized by anycombination of a system, method, integrated circuit, computer program,and recording medium.

Preferred embodiments to carry out the present disclosure will bedescribed below with reference to the attached drawings. It should benoted that the second embodiment is the closest embodiment to thedisclosure in claim 1 of the present application, but the basicconfiguration of the information recording medium and so forth in thesecond embodiment will be described first by way of the firstembodiment, to facilitate understanding.

First Embodiment

First, the basic structure and operations of a BD-ROM and a BD-ROMplayer that plays BD-ROMs will be described with reference to FIGS. 1through. 30.

Logical Data Structure on Disc

FIG. 4 is a diagram illustrating data hierarchy on a BD-ROM. Asillustrated in FIG. 4, there are recorded in a BD-ROM 104 that is a discmedium, AV data 103, BD management information 102 such as managementinformation relating to the AV data, AV playback sequence, and so forth,and a BD playback program 101 that realizes interactivity.

Note that in the present embodiment, description of BD-ROM will be madeprimarily with regard to an AV application that plays AV contents suchas movies, but a BD-ROM can be used as a recording medium for computeruse, in the same way as with CD-ROMs and DVD-ROMs, as a matter ofcourse.

FIG. 5 is a diagram illustrating the structure of logical data recordedon the above BD-ROM 104. The BD-ROM 104 has a recording region in theform of a spiral from the inner perimeter thereof toward the outerperimeter, and has a logical address space where logical data can berecorded, between a read-in at the inner perimeter and a read-out at theouter perimeter, in the same way as with other optical discs, such asDVDs and CDs, for example.

On the inner side of the read-in there is a special region called aBurst Cutting Area (BCA), that can only be read out by the drive. Thisregion is unreadable by applications, and accordingly is often used incopyright protection technology and so forth, for example.

Application data such as video data and the like is recorded the logicaladdress space, with file system information (volume) at the beginningthereof. The file system is the arrangement for managing data stipulatedby a standard such as UDF or ISO9660 or the like, as described above inthe conventional art. Logical data recorded therein can be read outusing the directory and file structure, in the same way as with a normalPC.

In the case of the present embodiment, the directory and file structureon the BD-ROM 104 has a BDVIDEO directory immediately below the rootdirectory (ROOT). This directory is a directory in which data, such asAV data and management information handled by the BD-ROM (the BDplayback program 101, BD management information 102, and AV data 103illustrated in FIG. 4) is recorded. The following seven types of filesare recorded beneath the BDVIDEO directory.

BD.INFO (Fixed Filename)

This is one of “BD management information”, and is a file in which isrecorded information relating to the entire BD-ROM. The BD-ROM playerreads out this file first.

BD.PROG (Fixed Filename)

This is one of “BD playback programs”, and is a file in which isrecorded a program relating to the entire BD-ROM.

XXX. PL (“XXX” is variable, suffix “PL” is fixed)

This is one of “BD management information”, and is a file in which isrecorded playlist (Play List) information that records a scenario. Eachplaylist has one file.

XXX.PROG (“XXX” is variable, suffix “PROG” is fixed)

This is one of “BD playback programs”, and is a file in which isrecorded a program for each aforementioned playlist. The correlation tothe playlist is identified by the file body name (“XXX” matches).

YYY.VOB (“YYY” is variable, suffix “VOB” is fixed)

This is one of “AV data”, and is a file in which is recorded a VOB (thesame as the VOB described in the conventional example). One VOBcorresponds to one file.

YYY.VOBI (“YYY” is variable, suffix “VOBI” is fixed)

This is one of “BD management information”, and is a file in which isrecorded management information relating to the VOB which is AV data.The correlation to the VOB is identified by the file body name (“YYY”matches).

ZZZ.PNG (“ZZZ” is variable, suffix “PNG” is fixed)

This is one of “AV data”, and is a file in PNG (an image formatstandardized by the World Wide Web Consortium (W3C) and is pronounced“ping”) which is image data for configuring subtitles and menu screens.One PNG image corresponds to one file.

Player Configuration

Next, the configuration of a player that plays the BD-ROM 104 will bedescribed with reference to FIGS. 6 and 7. FIG. 6 is a schematic diagramillustrating the basic configuration of a BD-ROM player that plays theBD-ROM 104.

The BD-ROM player illustrated in FIG. 6 reads out data on the BD-ROM 104via an optical pickup 202. The data that is read out is stored indedicated memory in accordance with the type of each data.

The BD playback program (“BD.PROG” or “XXX.PROG” file) is recorded inprogram recording memory 203, the BD management information (“BD.INFO”,“XXX.PL”, or “YYY.VOBI” file) in management information recording memory204, and AV data (“YYY.VOB” or “ZZZ.PNG” file) in AV recording memory205, respectively.

The BD playback program recorded in the program recording memory 203 isprocessed by a program processing unit 206. The BD managementinformation recorded in the management information recording memory 204is processed by a management information processing unit 207. Also, theAV data recorded in the AV recording memory 205 is processed by apresentation processing unit 208.

The program processing unit 206 receives information of a playlist to beplayed from and event information such as the timing to execute aprogram from the management information processing unit 207, andperforms processing of the program. The playlist to play can bedynamically changed at the program, and this can be realized by sendinga play command of the playlist after changing to the managementinformation processing unit 207.

The program processing unit 206 further accepts events from the user,such as requests from a remote controller that the user operates forexample, and in a case where there is a program corresponding to theuser event, executes the processing.

The management information processing unit 207 receives instructionsfrom the program processing unit 206 and analyzes a playlistcorresponding to that instruction and the management information of aVOB corresponding to that playlist. Further, instructions of AV data tobe played are given to the presentation processing unit 208. Themanagement information processing unit 207 also receives reference timeinformation from the presentation processing unit 208, and performsstopping instruction of the AV data playback to the presentationprocessing unit 208 based on the time information. Further, an event isgenerated indicating the program executing timing as to the programprocessing unit 206.

The presentation processing unit 208 has decoders corresponding to eachdata of video, audio, and subtitles, and decodes and outputs AV data inaccordance with instructions from the management information processingunit 207. The video data and subtitle data is drawn on respectivededicated planes after decoding.

Specifically, the video data is drawn on a video plane 210, and imagedata such as subtitle data is drawn on an image plane 209, further,compositing processing of the video drawn on the two planes is performedby a compositing processing unit 211 and output to a display device suchas a TV or the like.

The BD-ROM player has a configuration based on the data structurerecorded in the BD-ROM 104 illustrated in FIG. 4, as illustrated in FIG.6. FIG. 7 is a block diagram detailing the configuration of the playerillustrated in FIG. 6. The correlation of the components illustrated inFIG. 6 and the components illustrated in FIG. 7 is as follows.

The AV recording memory 205 corresponds to image memory 308 and a trackbuffer 309. The program processing unit 206 corresponds to a programprocessor 302 and a UO (User Operation) manager 303. The managementinformation processing unit 207 corresponds to a scenario processor 305and a presentation controller 306. The presentation processing unit 208corresponds to a clock 307, a demultiplexer 310, an image processor 311,a video processor 312, and a sound processor 313.

The VOB data (MPEG stream) read out from the BD-ROM 104 is recorded inthe track buffer 309, and the image data (PNG) in the image memory 308.

The demultiplexer 310 extracts VOB data recorded in the track buffer309, based on the time obtained from the clock 307. Further, video dataincluded in the VOB data is sent to the video processor 312, and theaudio data to the sound processor 313.

The video processor 312 and sound processor 313 each are configuredincluding a decoder buffer and a decoder, as stipulated by the MPEGsystem standard. That is to say, the data of each of the video and audiosent from the demultiplexer 310 is temporarily recorded in therespective decoder buffers, and subjected to decoding processing at therespective decoders following the clock 307.

There are the following two processing methods for the PNG data recordedin the image memory 308. In a case where the PNG data is for subtitles,the decoding timing is instructed by the presentation controller 306.The scenario processor 305 first receives the time information from theclock 307, and instructs the presentation controller 306 to display ornot display subtitles when the subtitle display time (starting andending) arrives, so that appropriate subtitle display can be performed.

The image processor 311 which has received a decode/display instructionfrom the presentation controller 306 extracts the corresponding PNG datafrom the image memory 308, decodes, and draws on the image plane 209.

Also, in a case where the PNG data is for a menu screen, the decodingtiming is instructed by the program processor 302. When the programprocessor 302 instructs decoding of the image is dependent on the BDprogram that the program processor 302 is processing, and accordingly isnot always the same.

The image data and video data is drawn on the image plane 209 and videoplane 210 after the respective decoding described in FIG. 6, andcomposited and output by the compositing processing unit 211.

The management information read out from the BD-ROM 104 (scenario and AVmanagement information) is recorded in the management informationrecording memory 204, but the scenario information (“BD.INFO” and “XXX.PL”) is read out and processed by the scenario processor 305. Also, theAV management information (“YYY.VOBI”) is read out and processed by thepresentation controller 306.

The scenario processor 305 analyzes the playlist information, instructsthe presentation controller 306 of the VOB referenced by the playlistand the playback position thereof. The presentation controller 306analyzes the management information (“YYY.VOBI”) of the VOB to behandled, and instructs a drive controller 317 to read out the VOB to behandled.

The drive controller 317 follows the instructions of the presentationcontroller 306 to move the optical pickup 202, and read out the AV datato be handled. The AV data that has been read out is recorded in theimage memory 308 or track buffer 309, as described earlier.

The scenario processor 305 monitors the time of the clock 307, and handsthe event to the program processor 302 at the timing set in themanagement information.

The BD program recorded in the program recording memory 203 (“BD.PROG”or “XXX.PROG”) is executed by the program processor 302. The programprocessor 302 processes a BD program in a case where an event has beensent from the scenario processor 305 or a case where an event has beensent from the UO manager 303.

In a case where a request has been sent from the user by a remotecontroller key, the UO manager 303 generates an event corresponding tothis request, and sends to the program processor 302. Playback of aBD-ROM is performed by the operations of the components in this way.

Application Space

FIG. 8 is a diagram illustrating application space of a BD-ROM. In theapplication space of a BD-ROM, a playlist (PlayList) is one playbackunit. A playlist has a static scenario that is made up of a playbacksequence of cells (Cell), and a dynamic scenario described by a program.

As long as there is no dynamic scenario according to a program, theplaylist is simply playing the individual cells in order, and playbackof the playlist ends at the point that playback of all cells has ended.On the other hand, a program is capable of describing playback beyondthe playlist, and dynamically changing the object of playback inaccordion with user selections or the state of the player. A typicalexample is dynamic change of the object of playback made via the menusscreen. In the case of a BD-ROM, a menu is a scenario played by userselection, i.e., one component of a function to dynamically select aplaylist.

The term program as used here means an event handler executed by atime-based event or a user event. A time-based event is an eventgenerated based on time information embedded in the playlist. An eventsent from the scenario processor 305 to the program processor 302 asdescribed in FIG. 7 corresponds to this. Upon a time-based event beingissued, the program processor 302 process execution of an event handlercorrelated by ID.

As described earlier, a program to be executed may instruct playback ofanother playlist, and in this case, the playback of the playlistcurrently being played is canceled, and transitions to playback of thespecified playlist.

A user event is an event generated by operations of remote controllerkeys by the user. There are two general types of user events. A first isan event of selecting a menu generated by operations of cursor keys(“up”, “down”, “left”, and “right” keys) and an “OK” key that the remotecontroller has.

The event handler corresponding to the event of menu selection is onlyvalid for restricted time within the playlist. That is to say, validityperiods are set for each of the event handles, as playlist information.The program processor 302 searches for a valid event handler when an“up”, “down”, “left”, “right”, or “OK” key has been pressed, and in acase where there is a valid event handler, the event handler isexecuted. Otherwise, the event of menu selection is ignored.

The second user event is an event for calling up a menu screen generatedby operation of a “menu” key. Upon a menu screen call-up event beinggenerated, a global event handler is called.

A global event handler is an event handler that is not dependent on anyplaylist, and is constantly valid. Using this function enables a DVDmenu call to be implemented. Implementing a menu call enables audio andsubtitle menus and so forth to be called up during playback of a title,and to execute playback of the title from the paused point where theaudio or subtitles was changed.

A cell (Cell), which is a unit making up a static scenario in theplaylist, is a reference to all or part of a playback section of a VOB(MPEG stream). A cell has information of starting and ending time of theplayback section within the VOB. VOB management information (VOBI), thatis paired with each VOB, has a time map (Time Map or TM) therein, andcan find the readout start address and end address for the playback andend time of the VOB within the VOB (i.e., within the object file“YYY.VOB”) described by this time map. Details of the time map will bedescribed later with reference to FIG. 14.

Details of VOB

FIG. 9 is a diagram illustrating the configuration of an MPEG stream(VOB) used in the present embodiment. As illustrated in FIG. 9, a VOB ismade up of multiple Video Object Units (VOBU). A VOBU is a unit based ona Group Of Pictures (GOP) in a MPEG video stream, and is one playbackunit in a multiplexed stream including audio data.

A VOBU has playback time of 0.4 seconds to 1.0 seconds, and normally hasplayback time of 0.5 seconds. This is due to the MPEG GOP structurenormally being 15 frames/second (in the case of NTSC).

A VOBU has a video pack (V_PCK) that is video data and an audio pack(A_PCK) that is audio data therein. Each pack is configured of 1 sector,and in the case of the present embodiment is configured in 2 kB units.

FIG. 10 is a diagram illustrating the configuration of a pack in an MPEGstream. Elementary data such as video data and audio data aresequentially input from the beginning of a data storage region in apacket, called a payload, as illustrated in FIG. 10. A packet header isattached to a payload, making up one packet.

Recorded in the packet header is an ID (stream_id) for identifying whichstream the data stored the payload belongs to, whether video data oraudio data, and in a case there are multiple streams worth of video dataor audio data, which stream the data belongs to, and a Decode Time Stamp(DTS) and Presentation Time Stamp (PTS) that are timestamps for thedecoding and displaying time information of this payload.

Not all packet headers necessarily have a DTS and PTS recorded; rulesfor recording are stipulated in MPEG. Details of the rules are laidforth in the MPEG system (ISO/IEC13818-1) Standard, and accordingly willbe omitted here.

A header (pack header) is further added to the packet, thereby making upa pack. The pack header has recorded therein a System Clock Reference(SCR) that is a timestamp indicating when this pack passes through thedemultiplexer 310 and is to be input to decoder buffers of theindividual elementary streams.

Interleaved Recording of VOB

Interleaved recorded of VOB files will be described with reference toFIGS. 11 and 12. FIG. 11 is a diagram for describing the relationshipbetween the AV data and the configuration of a BD-ROM player.

The drawing at the upper tier in FIG. 11 is part of the playerconfiguration diagram described above with reference to FIG. 7. The datain the BD-ROM is passes through the optical pickup 202 and is input tothe track buffer 309 if a VOB, i.e., an MPEG stream, and input to theimage memory 308 if a PNG, i.e., image data.

The track buffer 309 is a First-In First-Out (FIFO), with input VOB databeing sent to the demultiplexer 310 in the order in which it was input.At this time, the individual packs are extracted from the track buffer309 according to the aforementioned SCR, and data is delivered to thevideo processor 312 or sound processor 313 via the demultiplexer 310.

On the other hand, In a case of image data, which image to draw isinstructed by the presentation controller 306 (see FIG. 7). The imagedata used for drawing is deleted from the image memory 308 at the sametime if image data for subtitles, but is retained in the image memory308 if image data for a menu. This is because drawing of the menu isdependent on user operations, so there is the possibility that the sameimage will be drawn multiple times.

The drawing at the lower tier in FIG. 11 is a diagram illustratinginterleaved recording of a VOB file and PNG files on the BD-ROM.Generally, in the case of ROM, such as CD-ROM or DVD-ROM for example, AVdata that is a series of continuous playing units is recordedcontinuously. As long as the data is recorded continuously, all thedrive has to do is to sequentially read out the data and deliver it tothe player side.

However, in a case where the AV data to be continuously play isfragmented and dispersed across the disc, seek operations are interposedbetween the individual continuous sections, and data readout stopsduring this time. That is to say, supply of data may stop.

In the same way, recording of a VOB file in a continuous region isdesirable for BD-ROMs as well, but there is data such as subtitle datafor example, that is to be played synchronously with the video data inthe VOB, so the subtitle data needs to be read out from the BD-ROM inone way or another.

One way of reading out subtitle data is to read out all subtitle imagedata (PNG file) before starting playback of the VOB. However in thiscase, a great amount of memory is necessary to use for temporaryrecording, so this is not realistic. Accordingly, method where a VOBfile is divided into several blocks, and the VOB file and image data aresubjected to interleaved recording is employed with the presentembodiment.

The lower tier in FIG. 11 is a diagram for describing interleavedrecording. By suitably performing interleaved placement of the VOB fileand image data, image data can be stored in the image memory 308 at anecessary timing, without the great amount of temporary recording memorydescribed above. However, while the image data is being read out,readout of VOB data stops, as a matter of course.

FIG. 12 is a diagram for describing a VOB data continuous supply modelusing the track buffer 309, to solve the above problem in interleavedrecording. As described earlier, VOB data is temporarily stored in thetrack buffer 309. Setting the data input rate to the track buffer 309 tobe higher than the data output rate from the track buffer 309 means thatthe amount of data sorted in the track buffer 309 continues to increase,as long as data is being read out from the BD-ROM.

Now, the input rate to the track buffer 309 is denoted by Va, and theoutput rate from the track buffer 309 is denoted by Vb. The continuousrecording region of the VOB continues from “a1” to “a2” as illustratedin the drawing at the upper tier in FIG. 12. From “a2” to “a3” is asection where image data is recorded, so VOB data cannot be read out.

The drawing at the lower tier in FIG. 12 is a diagram illustrating thestored amount in the track buffer 309. The horizontal axis representstime, and the vertical axis represents the amount of data sorted insidethe track buffer 309. The time “t1” indicates the time at which readoutof the continuous recording region of the VOB “a1” has started.

After this time, data will be accumulated in the track buffer 309 at arate of Va−Vb. It is needless to say that this is the difference in theinput/output rates of the track buffer 309. Time “t2” is the time toread in data at “a2”, and is the end point of one continuous recordingregion.

That is to say, the amount of data in the track buffer 309 increases atthe rate of Va−Vb from “t1” to “t2”, and the data accumulation amountB(t2) at the time “t2” can be calculated by the following (Expression1).

B(t2)=(Va−Vb)×(t2−t1)  (Expression 1)

Thereafter, image data continues until the address “a3” on the BD-ROM,so input to the track buffer 309 is 0, and the amount of data within thetrack buffer 309 decreases at an output rate “−Vb”. This reduction indata amount continues until the readout position “a3”, i.e., until thetime “t3”.

What is important here is that once the data amount stored in the trackbuffer 309 before time “t3” reaches 0, there is no more VOB data tosupply to the decoder, so playback of the VOB will stop. However, in acase where the is data remaining in the track buffer 309 at time “t3”,this means that playback of the VOB can be continued without stopping.

The conditions for the VOB playback to be continuously performed withoutstopping can be expressed by the following (Expression 2).

B(t2)≧−Vb×(t3−t2)  (Expression 2)

That is to say, the array of image data should be decided so as tosatisfy (Expression 2).

Navigation Data Structure

The structure of navigation data (BD management information) recorded inthe BD-ROM will be described with reference to FIGS. 13 through 19. FIG.13 is a diagram illustrating the internal structure of a VOB managementinformation file (“YYY.VOBI”).

The VOB management information has stream attribute information(Attribute) and a time map (TMAP) of this VOB. The stream attributeinformation is of a configuration having video attributes (Video) andaudio attributes (Audio#0 through Audio#m) individually. Particularly,in the case of an audio stream, the VOB can have multiple audio streamsat the same time, so the number of data fields of the audio attributesis identified by the number of audio streams (Number).

The following is an example of fields that the video attributes (Video)have, and values which each can have.

Compression format (Coding):

-   -   MPEG1    -   MPEG2    -   MPEG4

Resolution (Resolution):

-   -   1920×1080    -   1280×720    -   720×480    -   720×565

Aspect ratio (Aspect):

-   -   4:3    -   16:9

Frame rate (Framerate):

-   -   60    -   59.94    -   50    -   30    -   29.97    -   25    -   24

The following are example of fields that the audio attributes (Audio)have, and values which each can have.

Compression format (Coding):

-   -   AC3    -   MPEG1    -   MPEG2    -   LPCM

Number of channels (Ch):

-   -   1 to 8

Language attributes (Language):

-   -   JPN, ENG, . . . .

The time map (TMAP) is a table having information for each VOBU, andholds the number of VOBUs (Number) that the VOB has, and each VOBUinformation (VOBU#1 through VOBU#n). Each VOBU information has aplaytime length (Duration) of the VOBU and data size (Size) of the VOBU.

FIG. 14 is a diagram for describing the details of VOBU information. Itis widely known that the MPEG stream has aspects regarding two physicalamounts, a temporal aspect and a data-size aspect. For example, AudioCode number 3 (AC3) that is an audio compression standard performscompression at a fixed bitrate, so the relationship between time andaddress can be obtained by a primary expression.

However, in the case of MPEG video data, each frame has a fixed displaytime such as 1/29.97 seconds in the case of NTSC for example, but thedata size of each frame after compression will vary greatly depending onthe picture properties and the picture type used in compression, whichare the so-called I/P/B pictures. Accordingly, it is impossible toexpression the relationship between time and address by a commonexpression in the case of MPEG video.

As a matter of course, it is impossible to expression the relationshipbetween time and data by a common expression, with regard to an MPEGstream where MPEG video data has been multiplexed, i.e., a VOB, as well.Instead, the relationship between time and address within the VOB isassociated by a time map (TMAP). A table which has the number of framesin each VOBU and the number of packs in the VOBU as entries is the timemap (TMAP), as illustrated in FIG. 14.

How to use a time map (TMAP) will be described with reference to FIG.15. FIG. 15 is a diagram for describing an address informationacquisition method using a time map.

In a case where time information (Time) is provided, as illustrated inFIG. 15, first, to which VOBU that time belongs is searched for.Specifically, the number of frames is added for each VOBU in the timemap, and the VOBU where the sum of the number of frames exceeds ormatches the value obtained by converting this time into the number offrames is the VOBU that corresponds to this time.

Next, the size for each VOBU in the time map are added up to the VOBUimmediately preceding this VOBU, and that values is the beginningaddress (Address) of the pack to be read out to play the frame includingthe time that has been given. Accordingly, an address corresponding togiven time information can be obtained in an MPEG stream.

Next, the internal structure of the playlist (“XXX.PL”) will bedescribed with reference to FIG. 16. FIG. 16 is a diagram illustratingthe configuration of a playlist.

A playlist is made up of a cell list (CellList) and event list(EventList). A cell list (CellList) is information indicating theplayback cell sequence within the playlist, and cells are played in theorder of description in this list. The content of a cell list (CellList)is the number of cells (Number) and information of each cell (Cell#1through Cell#n).

The information of each cell (Cell#1 through Cell#n) has the VOBfilename (VOBName), the valid section start time (In) and valid sectionend time (Out) in this VOB, and a subtitle table (SubtitleTable).

The valid section start time (In) and valid section end time (Out) areeach expressed by frame No. within this VOB, and the address for VOBdata necessary for playback can be obtained by using the above-describedtime map (TMAP).

The subtitle table (SubtitleTable) is a table having subtitleinformation that is synchronously played with this VOB. The subtitlesmay have multiple languages, in the same way as with the audio. Thesubtitle table (SubtitleTable) is made up of the number of languages(Number) and a subsequent table for each language (Language#1 throughLanguage#k).

The table for each language (Language#1 through Language#k) is made upof language information (Language), the number of pieces of subtitleinformation of the subtitles to be displayed (Number) The subtitleinformation of the subtitles to be displayed (Speech#1 throughSpeech#j). Each subtitle information (Speech#1 through Speech#j) is madeup of a corresponding image data filename (Name), subtitle display starttime (In) and subtitle display end time (Out), and subtitle displayposition (Position).

The event list (EventList) is a table defining events occurring withinthis playlist. The event list is made up of the number of events(Number), and following the individual events (Event#1 through Event#m),each event (Event#1 through Event#m) being made up of event type (Type),event ID (ID), event generation time (Time), and valid period(Duration).

FIG. 17 is a diagram illustrating the configuration of an event handlertable (“XXX.PROG”) that has an event handler (time-based events, anduser events for menu selection), for each playlist.

The event handler table contains the number of event handlers/programsthat are defined (Number), and individual event handlers/programs(Program#1 through Program#n).

The description within each of the event handlers/programs (Program#1through Program#n) contains a definition of the start the event handler(an <event_handler> tag) and an event handler ID (event_handler id) thatis paired with the aforementioned event ID. Following this, the programis described between brackets “{” and “}” after “function”.

Next, the information relating to the entire BD-ROM (“BD.INFO”) will bedescribed with reference to FIG. 18. FIG. 18 is a diagram illustratingthe configuration of BD.INFO which is overall BD-ROM information.

The overall BD-ROM information is made up of a title list (TitleList)and event list (EventList) for global events. The title list (TitleList)is made up of the number of titles in the disc (Number), andsubsequently each title information (Title#1 through Title#n).

Each title information (Title#1 through Title#n) includes a playlisttable (PLTable) and a chapter list within the title (ChapterList). Theplaylist table (PLTable) includes the number of playlist in the title(Number) and the playlist names (Name), i.e., the filenames of theplaylists.

The chapter list (ChapterList) is made up of the number of chaptersincluded in this title (Number), and each chapter information (Chapter#1through Chapter#n). Each chapter information (Chapter#1 throughChapter#n) has a table of cells that this chapter includes (CellTable),the cell table (CellTable) being made up of the number of cells (Number)and entry information of each cell (CellEntry#1 through CellEntry#k).Cell entry information (CellEntry#1 through CellEntry#k) is described asthe playlist name containing this cell and the cell No. within theplaylist.

The event list (EventList) has the number of global events (Number) andinformation of each global event (Event#1 through Event#m). What isnoteworthy here is that the global event that is defined first is calleda first event (FirstEvent), and is the event that is executed first whenthe BD-ROM is inserted into the player. Each global event information(Event#1 through Event#m) has only the event type (Type) and ID of theevent (ID).

FIG. 19 is a diagram illustrating the structure of the global eventhandler table (“BD.PROG”). This table is the same in content as theevent handler table described in FIG. 17, so description thereof will beomitted.

Mechanism of Event Occurrence

The mechanism of event occurrence will be described with reference toFIGS. 20 through 22. FIG. 20 is a diagram illustrating an example of atime event. As described above, a time event is defined by the eventlist (EventList) in the playlist (“XXX.PL”). In a case of an eventdefined as a time event, i.e., event type (Type) is “TimeEvent”, at thepoint of the event generation time (“t1”), a time event having the ID“Ex1” is output from the scenario processor 305 to the program processor302.

The program processor 302 searches for the handler that has the ID“Ex1”, and executes the relevant event handler. For example, in the caseof the present embodiment, a two-button image can be drawn, or the like.

FIG. 21 is a diagram illustrating an example of a user event due to auser having operated a menu. As described above, a user event due tomenu operations is also defined by the event list (EventList) in theplaylist (“XXX. PL”).

In the case of an event defined as a user event, i.e., in a case wherethe event type (type) is “UserEvent”, this user event is ready at thepoint that of reaching the event generation time (“t1”). At this time,the event itself is not generated yet. This event is in a ready stateduring the period (“T1”) described in the valid period information(Duration).

When a remote controller key “up”, “down”, “left”, or “right”, has beenpressed by the user, or when the “OK” key has been pressed, first, a UOevent is generated by the UO manager 303 and output to the programprocessor 302, as illustrated in FIG. 21.

The program processor 302 hands a UO event to the scenario processor305, and upon receiving the UO event, the scenario processor 305searches for whether or not a valid user event exists. In a case wherethere is a relevant user event as the result of the search, the scenarioprocessor 305 generates a user event, and outputs to the programprocessor 302.

The program processor 302 searches for an event handler having the eventID, in the case of the example illustrated in FIG. 21 for example,“Ev1”, and executes the relevant event handler. In the case of thisexample, playback of playlist#2 is started.

The generated user event does not include information regarding whichremote controller key has been pressed by the user. The information ofthe remote controller key that has been selected is notified to theprogram processor 302 by the UO event, and is recorded and held in aregister that the virtual player has. The program of the event handlercan check the value of this register and execute branching processing.

FIG. 22 is a diagram illustrating an example of a global event. Asdescribed earlier, a global event is defined in the event list(EventList) in the overall BD-ROM information (“BD.INFO”). An eventdefined as a global even, i.e., an event of which the event type (Type)is “Global Event”, is generated only in a case where the user hasoperated a remote controller key.

In a case where the user has pressed the menu key, first, a UO event isgenerated by the UO manager 303 and output to the program processor 302.The program processor 302 hands the UO event to the scenario processor305.

The scenario processor 305 generates the relevant global event, andsends it to the program processor 302. The program processor 302searches for an event handler having the event ID “menu”, and executesthis event handler. For example, in the case of the example illustratedin FIG. 22, playback of playlist#3 is started.

In the present embodiment, this is referred to simply as menu key, butthere may be multiple menu keys such as on the remote controller of aplayer that plays DVDs. Defining an ID corresponding to each menu keyenables appropriate processing to be performed as to each menu key.

Virtual Player Machine

FIG. 23 is a diagram for describing the functional configuration of theprogram processor 302. The functional configuration of the programprocessor 302 will be described with reference to FIG. 23.

The program processor 302 is a processing module that has a virtualplayer machine inside. A virtual player machine is a function modeldefined as a BD-ROM, and is not dependent on the implementation of eachBD-ROM player. That is to say, this guarantees that the same functioncan be executed in every BD-ROM player.

A virtual player machine has two major functions; programing functionsand player variables. The player variables are stored and held in aregister.

The programming functions are based on Java (registered trademark)Script, and the following three functions are defined as BD-ROM-uniquefunctions Link function: Stops the current playback, and starts playbackfrom specified playlist, cell, and time.

Link (PL#, Cell#, time)

-   -   PL#: playlist name    -   Cell#: cell No.    -   Time: time in cell to start playback        PNG drawing function: Draws specified PNG data on image plane        209.

Draw (File, X, Y)

-   -   File: PNG filename    -   X: X coordinate position    -   Y: Y coordinate position        Image plane clear function: Clears specified region of image        plane 209.

Clear (X, Y, W, H)

-   -   X: X coordinate position    -   Y: Y coordinate position    -   W: width in X direction    -   H: width in Y direction

The player variables include system parameters (SPRM) indicating settingvalues and so forth of the player, and general parameters (GPRM) usablein general uses.

FIG. 24 is a diagram illustrating a list of system parameters (SPRM).

-   -   SPRM(0): Language code    -   SPRM(1): Audio stream No.    -   SPRM(2): Subtitle stream No.    -   SPRM(3): Angle No.    -   SPRM(4): Title No.    -   SPRM(5): Chapter No.    -   SPRM(6): Program No.    -   SPRM(7): Cell No.    -   SPRM(8): Selected key information    -   SPRM(9): Navigation timer    -   SPRM(10): playback time information    -   SPRM(11): Mixing mode for karaoke    -   SPRM(12): Country information for parental    -   SPRM(13): Parental level    -   SPRM(14): Player setting value (video)    -   SPRM(15): Player setting value (audio)    -   SPRM(16): Language code for audio stream    -   SPRM(17): Language code for audio stream (extended)    -   SPRM(18): Language code for subtitle stream    -   SPRM(19): Language code for subtitle stream (extended)    -   SPRM(20): Player region code    -   SPRM(21): reserved    -   SPRM(22): reserved    -   SPRM(23): Playback state    -   SPRM(24): reserved    -   SPRM(25): reserved    -   SPRM(26): reserved    -   SPRM(27): reserved    -   SPRM(28): reserved    -   SPRM(29): reserved    -   SPRM(30): reserved    -   SPRM(31): reserved

Note that in the present embodiment, the programing functions of thevirtual player have been described as being based on Java (registeredtrademark) Script, Other programing functions may be used, such asB-Shell used in UNIX (registered trademark) OS or the like, Perl Script,and so forth, instead of Java (registered trademark) Script. In otherwords, the programing language in the present disclosure is notrestricted to Java (registered trademark) Script.

Example of Program

FIGS. 25 and 26 are diagrams illustrating an example of a program in theevent handler. FIG. 25 is a diagram illustrating an example of a programin an event handler according to control of a menu screen having twoselection buttons.

The program to the left side in FIG. 25 is executed using a time eventat the beginning of cell (PlayList#1.Cell#1). “1” is set to GPRM(0) herefirst, which is one of the general parameters. GPRM(0) is used in thisprogram to identify a button that is selected. A state where the button[1] situated on the left side has been selected is held as the initialstate.

Next, drawing of a PNG is performed for each of button [1] and button[2] using “Draw”, which is a drawing function. The button [1] is drawnas a PNG image “1black.png” with coordinates (10, 200) as the origin(upper left end). The button [2] is drawn as a PNG image “2white.png”with coordinates (330, 200) as the origin (upper left end).

At the end of this cell, the program to the right side in FIG. 25 isexecuted using a time event. A Link function is used here to instructplaying again from the beginning of this cell.

FIG. 26 is a diagram illustrating an example of a program in an eventhandler according to a user event for selection of a menu. In a casewhere any one of the remote controller keys of the “left” key, “right”key, or “OK” key has been pressed, the corresponding program is writtenin the event handler. In a case where the user has pressed a remotecontroller key, a user event is generated as described with reference toFIG. 21, and the event handler illustrated in FIG. 26 is activated.

The following branching processing is performed by this event handler,using the value of GPRM(0) identifying the selected button, and SPRM(8)identifying the selected remote controller key.

-   Condition 1) Case where button[1] is selected, and the selected key    is “right” key GPRM(0) is reset to 2, and the button in the selected    state is changed to the button[2] at the right.

The images of each of button[1] and button[2] are rewritten.

-   Condition 2) Case where the selected key is “OK” key, and button[1]    is selected Playback of playlist#2 is started.-   Condition 3) Case where the selected key is “OK” key, and button[2]    is selected Playback of playlist#3 is started.

The program illustrated in FIG. 26 is interpreted and executed asdescribed above.

Player Processing Flow

The flow of processing at the player will be described with reference toFIGS. 27 through 30. FIG. 27 is a flowchart illustrating the basic flowof playback of AV data in a BD-ROM player.

Upon a BD-ROM being inserted (S101), the BD-ROM player reads in andanalyzes “BD.INFO” (S102), and reads in “BD.PROG” (S103). “BD.INFO” and“BD.PROG” are both temporarily stored in the management informationrecording memory 204, and analyzed by the scenario processor 305.

Next, the scenario processor 305 generates the first event, inaccordance with the first event (FirstEvent) information in the“BD.INFO” file (S104). The generated first event is received by theprogram processor 302, which executes the event handler corresponding tothis event (S105).

It is expected that the event handler corresponding to the first eventwill have recorded therein information specifying a playlist to playfirst. If no playlist to play first is instructed, the player hasnothing to play, and simply awaits a user event to accept (No in S201).

Upon receiving a remote controller operation from the user (Yes inS201), the UO manager 303 generates a UO event for the program processor302 (S202).

The program processor 302 determines whether or not the UO event is dueto the menu key (S203), and in the case of the menu key (Yes in S203),hands the UO event to the scenario processor 305, and the scenarioprocessor 305 generates a user event (S204). The program processor 302executes the event handler corresponding to the generated user event(S205).

FIG. 28 is a flowchart illustrating the flow of processing in a BD-ROMplayer from starting to play a playlist until ending the VOB. Asdescribed earlier, playback of a playlist is started by the first eventhandler or global event handler (S301). The scenario processor 305 readsin and analyzes the playlist “XXX. PL” as necessary information to playa playlist that is the object of playback (S302), and reads in theprogram information “XXX.PROG” corresponding to the playlist (S303).

Next, the scenario processor 305 starts playback of the cell, based onthe cell information registered in the playlist (S304). Cell playbackmeans that a request is issued from the scenario processor to thepresentation controller 306, and the presentation controller 306 startsAV data playback (S305).

Once playback of AV data is started, the presentation controller 306reads in the VOB information file “YYY.VOBI” corresponding to the cellbeing played (S402) and analyzes it. The presentation controller 306identifies the VOBU for which to start playback and the address thereof,using the time map, and instructs the drive controller 317 of thereadout address. The drive controller 317 reads out the relevant VOBdata “YYY.VOB” (S403).

The VOB data that has been read out is sent to the decoder, and playbackis started (S404). VOB playback is continued until the playback sectionof this VOB ends (S405), and upon ending, if there is a next cell (Yesin S406), transitions to playback of Cell (S304). In a case where thereis no next cell (No in S406), the processing relating to playback ends.

FIGS. 29A and 29B are flowcharts illustrating the flow of eventprocessing from after having started AV data playback. FIG. 29A is aflowchart illustrating the flow of processing relating to a time eventin a BD-ROM player.

Note that the BD-ROM player is an event-driven player model. Whenplayback of a playlist is started, the time event related, user eventrelated, and subtitle display related event processing processes areeach activated, and event processing is executed in parallel.

When playback of playlist playback is started at the BD-ROM player(S501), confirmation is made that playlist playback has not ended (No inS502), and the scenario processor 305 confirms whether the time eventgeneration time has arrived (S503).

In a case where the time event generation time has arrived (Yes inS503), the scenario processor 305 generates a time event (S504). Theprogram processor 302 receives the time event, and executes the eventhandler (S505).

In a case where the time event generation time has not arrived (No inS503), and in a case where execution of the event handler has ended, theprocessing after confirmation of end of the playlist playback (S502) isrepeated.

In a case where confirmation is made that the playlist playback hasended (Yes in S502), the time event related processing is force-quit.

FIG. 29B is a flowchart illustrating the flow of processing relating toa user event in a BD-ROM player. When playback of playlist playback isstarted at the BD-ROM player (S601), confirmation is made that playlistplayback has not ended (No in S602), and the UO manager 303 confirmswhether a UO has been accepted.

In a case where there has been a UO accepted (Yes in S603), the UOmanager 303 generates a UO event (S604). The program processor 302accepts the UO event, and confirms whether the UO event is a menu callor not.

In the case of a menu call (Yes in S605), the program processor 302causes the scenario processor 305 to generate an event (S607), and theprogram processor 302 executes the event handler (S608).

On the other hand, in a case where determination is made that the UOevent is not a menu call (No in S605), this means that the UO event isan event due to a cursor key or the “OK” key. In this case, the scenarioprocessor 305 determines whether or not the current time is within thevalid period of the user event. If within the valid period (Yes in S606)the scenario processor 305 generates a user event (S607), and theprogram processor 302 executes the relevant event handler (S608).

In a case where there is no UO accepted (No in S603), the current timeis not within the valid period of the user event (No in S606), or theexecution of the event handler has ended, the processing followingconfirmation of the end of the playlist playback (S602) is repeated.

Upon confirmation of the end of the playlist playback (Yes in S602), theuser event related processing is force-quit.

FIG. 30 is a flowchart illustrating the flow of processing of subtitledata in the BD-ROM player. When playback of playlist playback is startedat the BD-ROM player (S701), confirmation is made that playlist playbackhas not ended (No in S702), and the scenario processor 305 confirmswhether the subtitle display start time has arrived or not. In a casewhere the subtitle display start time has arrived (Yes in S703), thescenario processor 305 instructs the presentation controller 306 to drawthe subtitle, and the presentation controller 306 instructs the imageprocessor 311 to draw the subtitle. The image processor 311 follows theinstruction to draw the subtitle on the image plane 209 (S704).

Also, in a case where the subtitle display start time has not arrived(No in S703), confirmation is made whether the subtitle display end timehas arrived. In a case where the subtitle display end time has arrived(Yes in S705), the presentation controller 306 instructs the imageprocessor 311 to erase the subtitle.

The image processor 311 erases the subtitle that has been drawn from theimage plane 209, in accordance with the instruction (S706).

In a case where the subtitle drawing by the image processor 311 (S704)has ended, a case where erasing of the subtitle by the image processor311 (S706) has ended, and a case where determination is made that thesubtitle display end time has not arrived (No in S705), the processingfollowing configuration of end of the playlist playback (S702) isrepeated.

Also, upon confirmation of the end of the playlist playback (Yes inS702), the subtitle related processing is force-quit.

According to the above operations, the BD-ROM player performs basicprocessing relating to BD-ROM playback based on user instructions or theBD management information recorded in the BD-ROM, and so forth.

Second Embodiment

Next, a second embodiment of the present disclosure will be described.The second embodiment is content relating to recording or playinghigh-luminance (HDR: High Dynamic Range) video information with a BD.The second embodiment is basically based on the first embodiment, so thefollowing description will be made primarily with regard to portionsthat are expanded in the second embodiment or portions that aredifferent.

FIGS. 31A and 31B illustrate a method of sending high-luminance metadatausing a video encoding format such as MPEG-4 AVC (also known as H.264)or HEVC (also known as H.265). Here, a unit made up of a picturereference configuration equivalent to a GOP (Group Of Pictures) used toimprove random accessibility in MPEG-2 Video is used as a GOP in MPEG-4AVC or HEVC, thereby encoding multiple pictures that have been grouped.

FIG. 31A indicates the encoding order of multiple Network AbstractionLayer (NAL) units in the first picture (first access unit) in the GOP.In the first picture in the GOP, there is a run of NALs of each of oneAU delimiter, one SPS, one or more PPS, 0 or multiple SEI messages, andone or more Slices making up the picture, followed if necessary by theNALs of Filler data, End of sequence, and End of stream.

In the SEI message (SEI(s)), Buffering period SEI message is followed byseveral other SEI messages if necessary. For example, several SEImessages including (1) a User data unregistered SEI message (GOP)indicating the reference relationship of pictures within this GOP, (2) aUser data unregistered SEI message (CC) indicating the Closed Captioninginformation of this picture, (3) a User data unregistered SEI message(HDRb) including standard and static high-luminance metadata indicatingthe luminance range such as the maximum luminance or minimum luminancein all of the pictures in this video sequence (VOB), (4) a User dataunregistered SEI message (HDRe) including dynamic high-luminancemetadata that is more detailed than the SEI message (HDRb), so as toindicate the luminance range such as the maximum luminance or minimumluminance in all of the pictures in this picture or GOP, and so forth,are encoded in this order.

The aforementioned SEI message (HDRb) or SEI message (HDRe) istransmitted along with the video information. This is to transmitinformation relating to luminance used at the time of mastering, and togive information regarding actually what level of brightness (cd/m̂2) theluminance value (Y) for each pixel obtained after the video informationis decoded.

For example, the SEI message (HDRb) or SEI message (HDRe) includecorrelation information between luminance that the pixels have andluminance at the time of mastering, such as, upon having decoded thevideo, the luminance of a pixel having a luminance value (Y) or 1000 was5000 cd/m̂2 when mastering. In a case where the maximum luminance (cd/m̂2)that can be expressed by a TV connected to the player is acquired,information for changing the dynamic range of the entire picture in theluminance direction may be carried by the aforementioned SEI message(HDRb) or SEI message (HDRe).

The SEI message (HDRb) is an SEI message transmitted in increments ofpictures or increments of GOPs to indicate an HDR video sequence, andtransmits information relating to static luminance information of theoverall video sequence (VOB). An HDR video sequence as used here means avideo sequence where a SEI message (HDRb) is recorded.

The SEI message (HDRe) that transmits information relating to dynamicluminance that is more detailed does not have to be recorded in the HDRvideo sequence, and an HDR video sequence does not have to have even onetherein. In a case where an SEI message (HDRe) exists, it is always anSEI message encoded immediately after an SEI message (HDRb),transmitting information relating to luminance in increments of picturesor increments of GOPs.

FIG. 31B illustrates the encoding order of multiple NAL units in apicture other than the first picture in the GOP (non-first access unit).In a picture that is not the first picture in the GOP, There is a run ofNALs of each of one AU delimiter, 0 or one PPS, 0 or multiple SEImessages, and one or more Slices making up the picture, followed ifnecessary by the NALs of Filler data, End of sequence, and End ofstream.

The SEI message (HDRb) or SEI message (HDRe) each store the aboveinformation, and is given to each picture according to the methodillustrated in FIGS. 31A and 31B. In a case of transmitting informationrelating to luminance in increments of GOPs, the SEI message (HDRb) andSEI message (HDRe) are both only given to the first picture in the GOP,and are not given to pictures that are not the first in the GOP at all.

FIG. 32 is a diagram illustrating a method of multiplexing an HDR videostream including up to an SEI message (HDRe) by MPEG-2 TS. Note that inthe present embodiment, the term sequence may mean the same as a stream,or may be part of a stream. After storing one picture (one frame or onevideo access unit) in one PES packet to put the HDR video stream into aPES, data in the PES packets are divided and stored in order in thepayload of PID=X TS packets.

In the case of the method illustrated in FIG. 32, the HDR video sequenceincluding up to the SEI message (HDRe) which is the PES packets ofstream_id=0xE1 is divided and stored in order in the TS packets of thesame PID (PID=X). Note that in a case of transmitting information of theSEI message (HDRe) at the time of outputting an HDR video sequence byHDMI (registered copyright) as in the method illustrated in FIG. 32,there are cases where the processing for searching for the SEI message(HDRe) from the entire video sequence may become sluggish.

FIG. 33 is a diagram for describing another method for multiplexing anHDR video stream including up to an SEI message (HDRe) by MPEG-2 TS. Onepicture (one frame or one video access unit) is stored in one PESpacket, to put the HDR video stream into a PES, and data in the PESpackets is divided and stored in order in the payloads of the TS packetsof both PID=X and Z.

In the case of the method illustrated in FIG. 33, the HDR video sequencewhich is the PES packets of stream_id=0xE1 is divided and stored inorder in the TS packets of PID=X, and just the SEI message (HDRe) isstored alone in the TS packet of PID=Z. At the time of outputting HDRvideo by HDMI (registered trademark), when the SEI message (HDRe)information is transmitted, only the SEI message (HDRe) is stored in theTS packet where PID=Z, as in the method illustrated in FIG. 33.Accordingly, the processing for searching for the SEI message (HDRe) islight.

Decoding just the HDR video sequence transmitted by TS packets of PID=Xis easy. However, in order to perform even higher luminance videoplayback including up to the SEI message (HDRe) needs additionalprocessing of transmitting the TS packets of both PID=X and Z to thesame TB buffer (an upstream buffer used in the T-STD model of the MPEG-2system).

FIG. 34 is a diagram for describing another method for multiplexing anHDR video stream including up to an SEI message (HDRe) by MPEG-2 TS. Onepicture (one frame or one video access unit) is divided and stored ineach of three PES packets, to put the video stream into a PES.Thereafter, each of the three PES packets are divided as necessary, andstored in order in the payload of the TS packets of PID=X.

In the case of the method illustrated in FIG. 34, the HDR video sequencewhich is two PES packets of stream_id=0xE1 is stored in the TS packetsof PID=X. Just the SEI message (HDRe) is stored alone in a TS packet ofthe same PID=X in the same stream_id=0xE1 but as a PES packet wherePES_priority=0.

At the time of outputting HDR video by HDMI (registered trademark), uponthe information of the SEI message (HDRe) being transmitted according tothe method illustrated in FIG. 34, the PES packet where stream_id=0xE1and PES_priority=0 is searched from each TS packet of PID=X.Accordingly, the processing for searching for the SEI message (HDRe) isnot as light as the method illustrated in FIG. 33.

However, there is little difference between decoding just the HDR videosequence transmitted by TS packets of PID=X and decoding not only theHDR video sequence but the SEI message (HDRe) included as well, so themethod illustrated in FIG. 34 is realizable.

Note that the PES_priority value does not have to be this combination;the same effect can be yielded by an arrangement where only the PESpacket storing the SEI message (HDRe) has a value of PES_priority=1.

FIG. 35 is a diagram for describing another method for multiplexing anHDR video stream including up to an SEI message (HDRe) by MPEG-2 TS. Thedifference as to the method illustrated in FIG. 34 is that thetransport_priority of the TS packet storing the PES packet containingthe SEI message (HDRe) is 0 in the method illustrated in FIG. 35.

At the time of outputting HDR video by HDMI (registered trademark), uponthe information of the SEI message (HDRe) being transmitted according tothe method illustrated in FIG. 35, the SEI message (HDRe) is analyzedfrom the TS packet where PID=X and transport_priority=0. Accordingly,the amount of processing to search for the SEI message (HDRe) is lightin the same way as the method illustrated in FIG. 33, so the methodillustrated in FIG. 35 is realizable.

Also, in this case, there is little difference in the T-STD modelbetween decoding just the HDR video sequence and decoding not only theHDR video sequence but also the SEI message (HDRe) included as well, sothe method illustrated in FIG. 35 is realizable. For example, the PIDdemultiplexer of the TS decoder separates the stream based on thetransport_priority value. Accordingly, a decoder that is not compatiblewith SEI message (HDRe) and performs high-luminance-izing usinginformation up to the SEI message (HDRb) can easily discard the TSpacket including the SEI message (HDRe) by the aforementioned PIDdemultiplexer.

Note that the transport_priority value does not have to be thiscombination; the same effect can be yielded by an arrangement where onlythe TS packet storing the SEI message (HDRe) has a value oftransport_priority=1.

FIG. 36 is a diagram for describing another method for multiplexing anHDR video stream including up to an SEI message (HDRe) by MPEG-2 TS. Themethod illustrated in FIG. 36 uses two types of PID as in the methodillustrated in FIG. 33, and configures the PES packets as in the methodillustrated in FIGS. 34 and 35. This method illustrated in FIG. 36 hasboth the same advantages and disadvantages as the method illustrated inFIG. 33.

FIG. 37 is a diagram for describing another method for multiplexing anHDR video stream including up to an SEI message (HDRe) by MPEG-2 TS. Themethod illustrated in FIG. 37 stores the SEI message (HDRe) in a PESpacket where PES_priority=0, which is a separate PES packet from the PESpacket storing the SEI message (HDRb) and so forth. After storing of theslice NAL units, the PES packet where PES_priority=0 is multiplexed atanother TS packet where PID=Z, separate from the TS packet where PID=X.The position of multiplexing of the SEI message (HDRe) is immediatelyafter the picture data. Accordingly, the method illustrated in FIG. 37stores the HDR video sequence up to the SEI message (HDRb) in one PESpacket. Other than this point, the method illustrated in FIG. 37 hasboth the same advantages and disadvantages as the method illustrated inFIG. 33.

FIG. 38 is a diagram for describing a method for multiplexing anenhanced video sequence, which is a different video sequence from an HDRvideo sequence, by MPEG-2 TS, instead of an SEI message (HDRe). Themethod illustrated in FIG. 38 transmits an enhanced video sequence(Enhancement layer video sequence) as enhancement video informationregarding an HDR video sequence (Base layer video sequence with userdata unregistered SEI message (HDRb)), instead of transmittinghigh-luminance enhancement metadata by SEI message (HDRe).

For example, an enhanced picture of Enhancement frame PES#n included inthe enhanced video sequence is added to the base picture of Base framePES#n included in the above-described HDR video sequence. Accordingly,high-luminance enhancement of the HDR video sequence can be performedmore accurately while using even more data than the SEI message.

Corresponding pictures may be correlated with each other by having thesame PTS. For example, correlation indicating that “PTS#b1 of basepicture”=“PTS#e1 of enhanced picture” is illustrated.

The above-described base video sequence and enhanced video sequence aremultiplied in the MPEG-2 TS as two entirely different video sequences inPES packets with different PIDs. In order to correctly specify the pairof the base video sequence and enhanced video sequence, the PMT packetmay express the pair using descriptor( ). For example, this methodillustrated in FIG. 38 describes HDR_pairing_descriptor( ) in the PMTpacket. The HDR_pairing_descriptor( ) contains the number of pairs inthis MPEG-2 TS (number_of_HDR_pairs), and the PID values that the basevideo sequence and enhanced video sequence use, for each pair. The PIDvalue used by the base video sequence is indicated bybase_layer_video_sequence_PID, and the PID value used by the enhancedvideo sequence is indicated by enhancement_layer_video_sequence_PID.Describing the HDR_pairing_descriptor( ) in this way enables a correctcombination of pairs to be indicated.

FIG. 39 is a diagram for describing attribute information in a case ofmanaging an HDR video stream by YYY.VOBI, which is managementinformation of a video stream (YYY.VOB). A number of attributes ofVideo, that is equal to the number of video streams included in YYY.VOB(V_Number), is recorded in “Attribute” of YYY.VOBI as video attributeinformation. Video attribute information in one video stream includesnot only coding method (Coding), spatial resolution (Resolution), aspectratio (Aspect), and frame rate (Framerate), but also the followingattribute information.

Attribute information is_HDR is information for identifying whether thevideo stream corresponding to this attribute information is an HDR videostream, or an SDR (Standard Dynamic Range) video stream. In a case wheredescription is made in is_HDR that the video stream is an HDR videostream (i.e., in a case where is_HDR=1b), the following attributeinformation relating to HDR is described.

Attribute information HDR_type indicates the type of video streamcorresponding to this attribute information, i.e., the type of HDR. Ofthe seven bits in the HDR_type, if the lowest 1 bit (b6) is 1b, thismeans that the video stream is an HDR video stream including an SEImessage (HDRb). In a case where the bit one order higher (b5) is 1b,this means that the video stream is a luminance-enhanced HDR videostream including an SEI message (HDRe). In a case where the bit oneorder higher (b4) is 1 b, this means that the video stream is anenhanced video sequence corresponding to a base video stream thatincludes an SEI message (HDRb).

Attribute information HDR_base_stream is information that identifies anHDR video stream (base video stream) including a base SEI message(HDRb), in a case where the video stream corresponding to this attributeinformation is a SEI message (HDRe) luminance-enhanced HDR video streamor an enhanced video sequence. For example, the information indicatesthe PID value of a TS packet in an HDR video stream (base video stream)including a base SEI message (HDRb). Accordingly, which video stream isthe base video stream paired with the video stream corresponding to theattribute information can be known without analyzing the stream, sosetting of the PID demultiplexer of the TS decoder can be appropriatelyperformed.

Attribute information Max_luminance represents the pixel luminance value(Y) of the maximum luminance (Max_luminance) of the HDR video streamwithin the video stream (YYY.VOB) corresponding to the attributeinformation, and further represents the luminance thereof in units ofcd/m̂2.

Attribute information Min_luminance represents the pixel luminance value(Y) of the minimum luminance (Min_luminance) of the HDR video streamwithin the video stream (YYY.VOB) corresponding to the attributeinformation, and further represents the luminance thereof in units ofcd/m̂2.

By analyzing this video attribute information, the player, which is theplayback device, can determine whether the video stream to be played isHDR or not. Further, if the video stream is HDR, the player candetermine what type of the HDR is, i.e., what encoding format the HDRvideo stream has. The player can also obtain the identificationinformation (PID) of the base HDR video stream corresponding to thevideo stream to be played, and information indicating luminance range,such as maximum luminance and minimum luminance.

Accordingly, HDR video can be played while performing suitable luminancecontrol.

Third Embodiment

Next, a third embodiment will be described. In the same way as in thesecond embodiment, the third embodiment is content relating to recordingor playing high-luminance video information with a BD. The thirdembodiment is basically based on the first and second embodiments, sothe following description will be made primarily with regard to portionsthat are expanded in the third embodiment or portions that aredifferent.

FIG. 40 is a diagram for describing the relationship among managementinformation (management information files) described in FIG. 5 and soforth, and the contents of description thereof.

The BD.INFO file is an management information file indicating attributesrelating to the entire BD, which is a recording medium. The BD.INFO fileincludes Disclnfo( ) describing representative attribute information ofthe entire disc, and Extension( ) describing extension data. Attributeinformation such as is_HDR, HDR_type, Max/Min_luminance, and so forth,are included in Extension( ), as HDR parameters.

The is_HDR is attribute information indicating whether or not this discincludes at least one or more PlayList (PlayList file) having is_HDR=1band/or VOBI file having is_HDR=1b. More specifically, is_HDR isattribute information indicating attributes of an initial video streamfirst played, out of the at least one video streams recorded in the BDthat is the recording medium, when the BD is inserted into the playbackdevice. That is to say, is_HDR indicates whether the dynamic range ofthe luminance of the initial video stream is a first dynamic range (SDR)or a second dynamic range (HDR) broader than the first dynamic range.The player can easily identify from this attribute information whetheror not the disc is a disc including an HDR video stream. Accordingly, ifthis is_HDR=1b at the time of the player outputting a first discplayback screen to a television by HDMI (registered trademark) or thelike, the player can perform processing such as starting transmissionwith signals indicating high-luminance video (HDR) attached.

HDR_type is attribute information indicating the type of the HDR videostreams recorded in this disc. That is to say, this is attributeinformation indicating whether or not each of predetermined multipletypes of video streams relating to dynamic range of luminance, are in atleast one video stream recorded in the BD. Specifically, if there is oneor more PlayList file of which one bit (b6) in HDR_type satisfies thecondition of 1b, and/or VOBI file satisfying that condition, in thisdisc, the lowest order one bit (b6) in HDR_type of the BD.INFO file isset to 1b; otherwise, 0b is set. If there is one or more PlayList fileof which one bit (b5) in HDR_type satisfies the condition of lb, and/orVOBI file satisfying that condition, in this disc, the one bit (b5) thatis one higher in HDR_type of the BD.INFO file is set to 1b; otherwise,0b is set. If there is one or more PlayList file of which one bit (b4)in HDR_type satisfies the condition of 1b, and/or VOBI file satisfyingthat condition, in this disc, the one bit (b4) that is one more higherin HDR_type of the BD.INFO file is set to 1b; otherwise, 0b is set.

Max/Min_luminance is attribute information indicating themaximum/minimum luminance of the HDR video streams recorded in thisdisc. The highest value of the Max_luminance values described in allPlayList files and/or VOBI files in this disc is described inMax_luminance. The lowest value of the Min_luminance values described inall PlayList files and/or VOBI files in this disc is described inMin_luminance.

The player can determine whether or not the disc to be played includesan HDR video stream, by analyzing each of the above-described attributeinformation of the BD.INFO file. Further, the player can determine whatsort of encoding format the HDR video stream is of if the disc includesan HDR video stream, and moreover, can obtain information ofmaximum/minimum luminance and so forth of the entire disc, and so forth.Accordingly, the HDR video stream can be played while performingsuitable luminance control processing.

XXX.PL file is a PlayList, and Extension( ) describing extension data ofthe PlayList is included in this XXX. PL file in addition to theabove-described information. Extension( ) includes attribute informationsuch as is_HDR, HDR_type, Max/Min_luminance, and so forth, as HDRparameters.

The is_HDR is attribute information indicating whether or not thisPlayList references at least one or more VOBI file having is_HDR=1b.According to this attribute information, the player can easily identifywhether or not this PlayList includes an HDR video stream. Accordingly,if this is_HDR=1b at the time of the player displaying a playback screenof a PlayList to a television by HDMI (registered trademark) or thelike, the player can perform processing such as starting transmissionwith signals indicating high-luminance video (HDR) attached.

HDR_type is attribute information indicating the type of the HDR videostreams this PlayList references. If this PlayList references one ormore VOBI of which one bit (b6) in HDR_type satisfies the condition of1b, the lowest order one bit (b6) in HDR_type of the PlayList is set to1b; otherwise, 0b is set. If this PlayList references one or more VOBIof which one bit (b5) in HDR_type satisfies the condition of 1b, the onebit (b5) that is one higher in HDR_type of the PlayList is set to 1b;otherwise, 0b is set. If this PlayList references one or more VOBI ofwhich one bit (b4) in HDR_type satisfies the condition of 1b, the onebit (b4) that is one more higher in HDR_type of the PlayList is set to1b; otherwise, 0b is set.

Max/Min_luminance is attribute information indicating themaximum/minimum luminance of the HDR video streams that this PlayListreferences. The highest value of the Max_luminance values described inall VOBI files that this PlayList references is described inMax_luminance. The lowest value of the Min_luminance values described inall VOBI files that this PlayList references is described inMin_luminance.

The player can determine whether or not the PlayList to be playedincludes an HDR video stream, by analyzing each of the above-describedattribute information of the XXX.PL file. Further, the player candetermine what sort of encoding format the HDR video stream is of if thePlayList includes an HDR video stream, and moreover, can obtaininformation of maximum/minimum luminance and so forth of the entirePlayList, and so forth. Accordingly, the HDR video can be played whileperforming suitable luminance control processing.

The YYY.VOBI file includes Extension( ) describing extension data of theVOBI in addition to the above-described information. Extension( )includes attribute information equivalent to the attribute informationillustrated in FIG. 39, as an HDR parameter.

Providing such attribute information to the VOBI hierarchy enables theplayer to easily recognize whether or not the video stream is HDR. Also,when generating or editing content, the authoring system that generatesdisc images, PlayList editing device (recorder) or the like, can easilyset values described in the PlayList file, such as is_HDR, HDR_type,HDR_base_stream, Max/Min_luminance, and so forth, from the VOBI file,without analyzing the video stream.

Storing the above-described attribute information in this way in thehierarchical levels in a database file enables the primary parameters(HDR parameters) relating to HDR to be determined for each hierarchicalincrement (e.g., three hierarchical levels of disc, playlist, andstream). As a result, advantages can be expected such as using theseprimary parameters for playback control or picture rendering for eachplayer, preventing streams from being analyzed at the time of editingprocessing, and so forth.

In this way, the BD according to the present embodiment has recordedtherein at least one video stream that is encoded video information, anda BD.INFO file indicating attributes relating to the entire BD. TheBD.INFO file includes is_HDR that indicates whether the dynamic range ofluminance of the initial video stream, of the at least one video stream,played first when the BD is inserted into the playback device, is SDR,or is HDR that is broader than SDR.

Accordingly, referencing the is_HDR in the BD.INFO file enables easydetermination of whether the dynamic range of luminance of the initialvideo stream is SDR or HDR, without analyzing the initial video stream.Thus, when the BD is inserted into the playback device, the playbackdevice references the is_HDR in the BD.INFO file, which enablesnegotiation based on HDMI (registered trademark) to be speedilyperformed with a display such as a television or the like, and theinitial video stream to be played. In this way, video streams and beefficiently recorded and managed, even in cases where there are variousforms for expressing the luminance of video streams.

Also, the BD according to the present embodiment has recorded therein atleast one video stream that is encoded video information, and a BD.INFOfile indicating attributes relating to the entire BD. The BD.INFO fileincludes HDR_type indicating whether or not at least one each ofmultiple types of predetermined video streams, relating to dynamic rangeof luminance, is recorded.

Accordingly, referencing the HDR_type in the BD.INFO file enables easydetermination of what types of video streams are corded in the BD. Thatis to say, determination can be made without analyzing the video streamsrecorded in the BD. For example determination can be easily maderegarding whether or not an SDR video stream, a video stream includingan SEI message (HDRb), a video stream including an SEI message (HDRe),and an enhanced video stream, are recorded in the BD. Thus, the playbackdevice references the HDR_type in the BD.INFO file, which enablesnegotiation based on HDMI (registered trademark) to be speedilyperformed with a display such as a television or the like, and the videostreams stored in the BD to be played. In this way, video streams can beefficiently recorded and managed, even in cases where there are variousforms for expressing the luminance of video streams.

FIG. 41 is a diagram for describing details of each of PlayList andVOBI, which are management information files. A PlayList includesCellList information (hereinafter referred to simply as CellList) andSubPL information (hereinafter referred to simply as SubPL), asillustrated in FIG. 41.

CellList is information bundling multiple Cell information (hereinafterreferred to simply as Cell). A Cell is information indicating oneplayback section of a video stream. Cell includes the filename of a VOBfile that this Cell references (VOBName), Closed Captioning information(CC), Cell start time information (In), Cell end time information (Out),and attribute information of elementary streams permitted to be playedin combination in this Cell (Combi). That is to say, if a video streamto be played is a base video stream (HDR video stream (HDRb)), theCellList in the PlayList describes the playback path of that base videostream.

Combi describes various types of information, for each elementary streamregarding which playback combination in this Cell is permitted. If apermitted elementary stream is a video stream, identifying informationof the video such as a PID (VideoPID), encoding attribute informationsuch as resolution, aspect, etc. (VideoFormat), and so forth, aredescribed.

If the permitted elementary stream is an enhanced video sequence(Enhancement layer video sequence) such as illustrated in FIG. 38,identifying information of the enhanced video sequence such as a PID(EnhVideoPID), bit depth information (EnhVideoBitDepth), maximumluminance information (EnhVideoMaxLum), and so forth. In the following,an enhanced video sequence is described as an enhanced video stream. Anenhanced video stream is a stream to enhance the luminance of the basevideo stream ‘HDR video stream (HDRb)).

SubPL is information specifying an additional sub-playback path, and forexample is information specifying an enhanced video stream to be playedin combination with an HDR video stream. That is to say, this SubPL hasdescribed therein a playback path of an enhanced video stream, so as tobe played at the same time as the above-described base video stream.

SubPL_type is information indicating the type of playback method of theHDR video stream and enhanced video stream. This information is used toidentify synchronous/asynchronous, or the number of streams being used(one or two), or the like.

Specifically, SubPL_type=0x0A (Synchronous Enhancement Layer Video SubPLin Sub TS) means that two system stream files (MPEG-2 TS) are used toread out the HDR video stream and enhanced video stream, and to playsynchronously. The meaning of being synchronous is that there is a fixedrelationship where a certain picture in the HDR video stream is alwaysand only played synchronously with a certain picture in the enhancedvideo stream.

SubPL_type=0x0B (Synchronous Enhancement Layer Video SubPL in Main TS)means that an HDR video stream and enhanced video stream in a singleMPEG-2 TS are played synchronously.

SubCellList included in SubPL is information bundling multiple SubCellinformation (hereinafter referred to simply as SubCell). SubCellincludes the filename of a VOB file (VOBName) that one continuoussection (SubCell) included in the enhanced video stream references, thestart time of the SubCell (In), the end time of the SubCell (Out), andidentification information of a Cell played at the same time (CellNum).Using SubPL in this way enables the player to be instructed regardingwhat sort of playback model and which file to use to play the HDR videostream (HDRb) and enhanced video stream (Enhancement Layer VideoStream).

In addition to the above-described information, a YYY.VOBI file hasVOB_type information added. VOB_type information indicates what sort ofusage this system stream (VOB) is used in. Specifically, VOB_type=0x01(Main TS for movie application) indicates a VOB (MPEG-2 TS stream) usedfor normal video playback such as movies and the like. VOB_type=0x10(Sub TS for Enhancement layer video stream) indicates a VOB (MPEG-2 TSstream) where an enhanced video stream has been multiplexed, that isonly usable by SubPL.

In this way, a BD according to the present embodiment has recordedtherein an HDR video stream (HDRb) that is encoded video information, anenhanced video stream that is encoded video information and is forenhancing luminance of the HDR video stream (HDRb), and a PlayList filedescribing the playback path of the HDR video stream (HDRb). ThePlayList file further describes the playback path of the enhanced videostream, so as to be played at the same time as the HDR video stream(HDRb).

Accordingly, not only the playback path of the HDR video stream (HDRb)but also the playback path of the enhanced video stream described asSubPL can also be easily identified by referencing the PlayList file.Therefore, the playback device can easily and appropriately multiplexthe enhanced video stream on the HDR video stream (HDRb) by referencingthe management information file, and consequently can appropriately playvideo information having a wide dynamic range. In this way, videostreams can be efficiently recorded and manages even in cases wherethere are various forms for expressing luminance of video streams.

FIG. 42 is a diagram for describing the meaning of each of the fields inmanagement information in a case where SubPL_type=0x0A. In theSubPL_type=0x0A playback model, two system stream files (MPEG-2 TS) areused to read out at the same time the HDR video stream (HDRb) from theMain TS and the enhanced video stream thereof (Enh. Layer Video) fromthe Sub TS, and play.

A playback section from Cell#0.In to Cell#0.Out in the HDR video stream(HDRb) is played as the playback section specified in Cell#0.Synchronously with this playback, a continuous section from SubCell#0.Into SubCell#0.Out in the enhanced video stream is played as thecontinuous section specified in SubCell#0. Accordingly, high-luminancevideo information that has higher luminance and higher quantizationprecision that the HDR video stream (HDRb) decoded at a decoder 401illustrated in FIG. 44, which will be described later, is output.

In the SubPL_type=0x0A playback model, two video streams are playedsynchronously, so Cell#0.In and SubCell#0.In are the same, andCell#0.Out and SubCell#0.Out are the same. Note that Cell#0.In,Cell#0.Out, SubCell#0.In and SubCell#0.Out are each points-in-timeexpressed by a PTS time axis. VOB_type=0x10 (Sub TS for Enh. LayerVideo) is only used for the playback mode of this SubPL_type=0x0A(Synchronous Enhancement Layer Video SubPL in Sub TS).

FIG. 43 is a diagram for describing the meaning of each of the fields inmanagement information in a case where SubPL_type=0x0B. In theSubPL_type=0x0B playback model, the HDR video stream (HDRb) and theenhanced video stream thereof are multiplied in one system stream file(MPEG-2 TS), and these streams are played at the same time. Thus, in theSubPL_type=0x0B model, the base video stream and enhanced video streamare multiplexed in the same transport stream. Accordingly, the basevideo stream and enhanced video stream can be clearly correlated, andvideo information having a wide dynamic range can be played in anappropriate manner.

Playback section from Cell#0.In to Cell#0.Out in the HDR video stream(HDRb) is played as the playback section specified in Cell#0.Synchronously with this playback, the continuous section fromSubCell#0.In to SubCell#0.Out in the enhanced video stream is played asthe continuous section specified in SubCell#0. Accordingly,high-luminance video information that has higher luminance and higherquantization precision that the HDR video stream (HDRb) decoded at thedecoder 401 illustrated in FIG. 44, which will be described later, isoutput.

Thus, in the SubPL_type=0x0B playback model, two video streams aremultiplexed in the same system stream file (Main TS that is MPEG-2 TS),and are played synchronously. Accordingly, Cell#0.In and SubCell#0.Inare the same, and Cell#0.Out and SubCell#0.Out are the same. That is tosay, The PlayList that is a management information file stores a firstsection included in the playback path of the base video stream, and asecond section included in the playback path of the enhanced videostream, mutually correlated with each other. The playback time of thefirst second and the second section is the same. Specifically, aplayback start time of the first section and a playback start time ofthe second section, that are the same time as each other, and further aplayback end time of the first section and a playback end time of thesecond section, that are the same time as each other, are described inthe PlayList. Accordingly, the base video stream and enhanced videostream can be appropriately synchronized and played.

FIG. 44 is a diagram for describing a decoder model of an HDR videostream according to the present embodiment. The playback deviceaccording to the present embodiment has a decoder system 400. Thedecoder system 400 is a video playback unit that reads out, from a BD,video streams such as the base video stream and enhanced video stream,and graphics data indicating subtitles and so forth, and playing, basedon the above-described management information files.

The decoder system 400 has a base decoder (Base Dec) 401, an enhanceddecoder (Enh. Dec) 402, a base plane (Base plane (HDRb)) 403, anenhanced plane (Enh. plane) 404, an enhanced plane (HDRe plane) 405, aBase+Enh. Plane 406, a subtitle decoder (Sub. Dec) 407, a subtitle plane(Subtitle Plane (8 bit)) 408, a graphics processor (GP) 409, ahigh-luminance subtitle plane (Subtitle Plane (HDRb/e)) 410, and ahigh-luminance subtitle plane (Subtitle Plane(Base+Enh.)) 411.

An HDR video stream containing an SEI message (HDRb) is decoded at abase decoder (Base Dec) 401. The high-luminance video informationgenerated by decoding the HDR video stream is rendered at a base plane(Base plane (HDRb)) 403. The basic luminance information (themaximum/minimum luminance values of the overall contents) and so forthincluded in the SEI message (HDRb) is transmitted along with thehigh-luminance video information, and output to an external video outputI/F such as HDMI (registered trademark).

The decoder system 400 that is a playback device compatible with SEImessages (HDRe) adds luminance enhancement information of the SEImessage (HDRe) to the high-luminance video information of the base plane(Base plane (HDRb)) 403, and renders the enhanced high-luminance videoinformation on an HDRe plane 405. The enhanced high-luminance videoinformation, that has had up to this SEI message (HDRe) added is outputto an external video output I/F such as HDMI (registered trademark),along with additional luminance information (by maximum luminance valueand minimum luminance value in increments of scenes) included in the SEImessage (HDRe).

The decoder system 400 that is a playback device compatible with theenhanced video stream described above decodes the enhanced video streamat the enhancement decoder (Enh. Dec) 402. The enhanced videoinformation generated by this decoding is rendered to an enhancementplane (Enh. plane) 404. The decoder system 400 composites this enhancedvideo information with the high-luminance video information at the baseplane (Base plane (HDRb)) 403, so as to composite videos that have thesame PTS. The enhanced high-luminance video information obtained by thiscompositing is rendered to a Base+Enh. Plane 406. The decoder system 400outputs this enhanced high-luminance video information to an externalvideo output I/F such as HDMI (registered trademark), along with basicluminance information transmitted by the SEI message (HDRb), luminanceenhancement information stored in the enhanced video stream, and soforth.

Now, graphics data to be superimposed on the video, e.g., a subtitlestream, is decoded at the subtitle decoder (Sub. Dec) 407, and therebyexpressed in 8-bit index color (256 colors). The subtitles that are thedecoded subtitle stream are rendered at the subtitle plane (SubtitlePlane (8 bit)) 408. The graphics processor (GP) 409 converts the 8-bitlevel YCrCb expressing the subtitles into 10-bit level YCrCb, andfurther converts the luminance of the subtitles from standard luminanceto high luminance (matching the high-luminance video information orenhanced high-luminance video information). The high-luminancesubtitles, that are subtitles converted to high luminance, are renderedto the high-luminance subtitle plane (Subtitle Plane (HDRb/e)) 410. Thehigh-luminance subtitles rendered to the high-luminance subtitle plane410 are then composited with the picture of the base plane (Base plane(HDRb)) 403 or enhanced plane (HDRe plane) 405, having the same time,and output.

Also, in a case where there is enhanced high-luminance video informationat the Base+Enh. Plane 406, or a SubPL_type=0x0A or 0x0B PlayList beingplayed, the graphics processor (GP) 409 converts the 8-bit level YCrCbexpressing the subtitles into 12-bit level YCrCb. Further, the graphicsprocessor (GP) 409 converts the luminance of the subtitles from standardluminance to high luminance (matching the enhanced high-luminance videoinformation generated using the enhanced video stream), forsuperimposing the subtitles in accordance with the enhanced videostream. The high-luminance subtitles, that are subtitles converted tohigher luminance, are rendered to the high-luminance subtitle plane(Subtitle Plane(Base+Enh.)) 411. The high-luminance subtitles renderedto the high-luminance subtitle plane (Subtitle Plane(Base+Enh.)) 411 arethen composited with the picture at the Base+Enh. Plane 406, having thesame time, and output.

Now, the graphics processor (GP) 409 acquires an index color table(CLUT) for subtitles rendered to the subtitle plane (Subtitle Plane (8bit)) 408, from the subtitle decoder (Sub. Dec) 407. This index colortable (CLUT) indicates whether the video information composited with thesubtitles is HDRb/HDRe video information, or enhanced high-luminancevideo information based on an enhanced video stream. The graphicsprocessor (GP) 409 determines whether to convert the 8-bit level YCrCbinto 10-bit level YCrCb or into 12-bit level YCrCb, based on this indexcolor table (CLUT). The graphics processor (GP) 409 then converts the8-bit level YCrCb in accordance with the determination results.

As described above, the decoder system 400 that is the video playbackunit of the present embodiment includes a first decoding unit made up ofthe base decoder (Base Dec) 401 and enhanced decoder (Enh. Dec) 402, asecond decoding unit made up of the subtitle decoder (Sub. Dec) 407, aprocessing unit made up of the graphics processor (GP) 409, and asuperimposing unit including the planes 403 through 406, 410, and 411.

The first decoding unit reads out the base video stream and the enhancedvideo stream from the BD and decodes these. The second decoding unitreads out encoded graphics data from the BD and decodes it. Theprocessing unit converts color of a predetermined number of levels (8bits), indicated by the decoded graphics data, into color of a number oflevels in accordance with the video plane for superimposing (10 bits or12 bits). The superimposing unit superimposes the enhanced video streamon the decoded base video stream and stores in a video plane, andfurther superimposes, upon the video stream stored in the video plane,graphics data expressed by the converted number of levels (10 bits or 12bits) of color.

Accordingly, the playback device according to the present embodiment canmake the color of subtitles, for example indicated by graphics data, toappropriately match the color of wide-dynamic-range video informationrealized using an enhanced video stream.

It should be noted that the above description is only an example, andthat one skilled in the art would be able to make various applications.

In the above embodiments, the components may be realized by a dedicatedhardware configuration, or by executing a software program suitable forthe components. The components may be realized by a program executingunit such as a CPU or processor reading out and executing a softwareprogram recorded in a recording medium such as a hard disk orsemiconductor memory or the like.

Although the playback device and playback method according to one ormultiple forms has been described by way of embodiments, the presentdisclosure is not restricted to these embodiments. Embodiments ofvarious modifications conceivable by one skilled in the art, and formsconfigured by combining components in different embodiments, may beincluded in the scope of the present disclosure without departing fromthe essence of the present disclosure.

The present disclosure enables video streams to be efficiently recordedand managed even in a case where there are various forms expressingluminance of video streams, and is applicable to, for example, opticaldiscs such as BDs, playback devices that read and play video streamsfrom the optical discs, and so forth.

What is claimed is:
 1. A recording medium, in which are recorded atleast one video stream that is encoded video information, and amanagement information file indicating attributes relating to the entirerecording medium, wherein the management information file includesattribute information indicating whether the dynamic range of luminanceof an initial video stream, which is played first out of the at leastone video stream when the recording medium is inserted into a playbackdevice, is a first dynamic range, or a second dynamic range that isbroader than the first dynamic range.
 2. A recording medium, in whichare recorded at least one video stream that is encoded videoinformation, and a management information file indicating attributesrelating to the entire recording medium, wherein the managementinformation file includes attribute information indicating whether ornot each of a predetermined plurality of types of video streams relatingto dynamic range of luminance are included in the at least one videostream.
 3. A recording medium, in which are recorded a base video streamthat is encoded video information, an enhanced video stream that isencoded video information, for enhancing luminance of the base videostream, and a management information file in which is described aplayback path of the base video stream, wherein a playback path of theenhanced video stream is further described in the management informationfile so as to be played at the same time as the base video stream. 4.The recording medium according to claim 3, wherein the base video streamand the enhanced video stream are multiplexed in the same transportstream.
 5. The recording medium according to claim 4, wherein a firstsection included in the playback path of the base video stream, and asecond section included in the playback path of the enhanced videostream, are described in the management information file in a mutuallycorrelated manner, and wherein playback time of the first section andthe second section is the same.
 6. The recording medium according toclaim 5, wherein a playback start time of the first section, and aplayback start time of the second section, that are the same time aseach other, are described in the management information file.
 7. Therecording medium according to claim 5, wherein a playback end time ofthe first section, and a playback end time of the second section, thatare the same time as each other, are described in the managementinformation file.
 8. A playback device that reads out and plays contentsfrom a recording medium, wherein, recorded in the recording medium areat least one video stream that is encoded video information, and amanagement information file indicating attributes relating to the entirerecording medium, wherein the management information file includesattribute information indicating whether the dynamic range of luminanceof an initial video stream, which is played first out of the at leastone video stream when the recording medium is inserted into a playbackdevice, is a first dynamic range, or a second dynamic range that isbroader than the first dynamic range, and wherein the playback deviceincludes a video playback unit that reads out and plays the initialvideo stream based on the management information file.
 9. A playbackdevice that reads out and plays contents from a recording medium,wherein, recorded in the recording medium are at least one video streamthat is encoded video information, and a management information fileindicating attributes relating to the entire recording medium, whereinthe management information file includes attribute informationindicating whether or not each of a predetermined plurality of types ofvideo streams relating to dynamic range of luminance are included in theat least one video stream, and wherein the playback device includes avideo playback unit that reads out and plays at least one video streambased on the management information file.
 10. A playback device thatreads out and plays contents from a recording medium, wherein, recordedin the recording medium are a base video stream that is encoded videoinformation, an enhanced video stream that is encoded video information,for enhancing luminance of the base video stream, and a managementinformation file in which is described a playback path of the base videostream, wherein a playback path of the enhanced video stream is furtherdescribed in the management information file so as to be played at thesame time as the base video stream, and wherein the playback deviceincludes a video playback unit that reads out and plays the base videostream and the enhanced video stream based on the management informationfile.
 11. The playback device according to claim 10, wherein the videoplayback unit includes a first decoding unit that reads out and decodesthe base video stream and the enhanced video stream from the recordingmedium, a second decoding unit that reads out and decodes encodedgraphics data from the recording medium, a processing unit that convertscolor of a predetermined number of levels indicated by the decodedgraphics data, into color of a predetermined number of levels inaccordance with a video plane that stores a video stream on which thegraphics data is to be superimposed, and a superimposing unit thatsuperimposes the decoded enhanced video stream on the decoded base videostream and stores at the video plane, and further superimposes graphicsdata expressed by color of the converted number of levels on the videostream stored at the video plane.
 12. A playback method of reading outand playing contents from a recording medium, wherein, recorded in therecording medium are at least one video stream that is encoded videoinformation, and a management information file indicating attributesrelating to the entire recording medium, wherein the playback methodmanagement information file includes attribute information indicatingwhether the dynamic range of luminance of an initial video stream, whichis played first out of the at least one video stream when the recordingmedium is inserted into a playback device, is a first dynamic range, ora second dynamic range that is broader than the first dynamic range, andwherein the initial video stream is read out and played based on themanagement information file.
 13. A playback method of reading out andplaying contents from a recording medium, wherein, recorded in therecording medium are at least one video stream that is encoded videoinformation, and a management information file indicating attributesrelating to the entire recording medium, wherein the managementinformation file includes attribute information indicating whether ornot each of a predetermined plurality of types of video streams relatingto dynamic range of luminance are included in the at least one videostream, and wherein the at least one video stream is read out and playedbased on the management information file.
 14. A playback method ofreading out and playing contents from a recording medium, wherein,recorded in the recording medium are a base video stream that is encodedvideo information, an enhanced video stream that is encoded videoinformation, for enhancing luminance of the base video stream, and amanagement information file in which is described a playback path of thebase video stream, wherein a playback path of the enhanced video streamis further described in the management information file so as to beplayed at the same time as the base video stream, and wherein the basevideo stream and enhanced video stream are read out and played based onthe management information file.